Thanks for sending this. I think the omission was deliberate, because of possible confusion with the controlLevelSwitch parameter accepted by the method. We should review this, as they're distinct, but there are some binary compatibility requirements around this method signature we'll also need to think through, so this could take a little while.

In the meantime, one possible workaround would be:

    .WriteTo.Conditional(
        evt => levelSwitch.IsEnabled(evt.Level),
        wt => wt.Seq(...))

@nblumhardt wow, thanks for the suggestion! it works perfectly fine for me.

Yet I think we should have the API I am suggesting in this PR. Primarily, to be on par with e.g. .ApplicationInsights() - they have both in their API. This way people would be less surprised and code more following POLA.

As for the breaking change - well, you know better your policies. But feels like it could be just enough to bump the major and have compilation-time compatibility. There is always as well a possibility to just introduce an overload. But you are smart people, you are aware of all of this 😉 So please take your time.

Thanks for the fast reply!